Hi @renezander030 . The issue with linting was when I ran the format almost all files were modified even though I touched only index. Js and test/showTemplates.js

In git status after running the lint more than 10 files modified message were showing.

That's why I gave the PR without linting.

Any solution for this?

Thanks.

Thanks @CaptainLevi25 — and good instinct holding the lint reformat back. You diagnosed it exactly right: npm run lint rewrites ~10 files you never touched because of pre-existing Biome debt in src/decorators.ts / src/draft.ts (noAssignInExpressions, noGlobalIsFinite, useTemplate, useOptionalChain). Folding those unrelated reformats into a feature PR would be the wrong call, so you did the right thing.

That one's on me — I'll clear the lint debt on master and pin Biome to an exact version in a separate commit. Once that lands, just merge/rebase master into your branch and CI will go green. Nothing for you to fix on the lint side.

Your actual change is clean: tests pass on Node 18/20/22 and src/index.ts has zero lint findings. Two small things on the PR itself:

1. README link label — the new bullet links [`template`] (singular), but the command is templates; please fix the visible label.
2. (optional) close the loop — apply-template reads a literal file path (readFileSync(templatePath)), so it won't resolve a bare slug like gold-title. Listing the slug is exactly what Add 'templates' command to list bundled templates (discoverability for apply-template) #11 asked for, so this is fine to merge as-is. If you want a nice follow-up, have templates also emit the resolvable path (e.g. a path field in the JSON + the path in the -H table) so users can paste straight into apply-template.

Fix the README label, and once I've cleared master + you rebase, I'll merge. Thanks for the clean work!

Correction to my last comment, @CaptainLevi25 — I dug into the CI log properly and I had it wrong. The pre-existing decorators.ts/draft.ts findings are warnings (intentionally non-blocking), so they're not what fails your build.

The one thing actually failing CI is a single error in your src/index.ts: the new imports aren't in Biome's required order (assist/source/organizeImports). It's a one-line fix — just alphabetize the node:fs named imports:

-import { existsSync, readFileSync, writeFileSync, readdirSync } from "node:fs";
+import { existsSync, readdirSync, readFileSync, writeFileSync } from "node:fs";

Or let Biome do exactly that one fix without touching anything else:

npx biome check --write --only=assist/source/organizeImports src/index.ts

That's the whole blocker — after it, biome check reports no errors and CI goes green. (Avoid biome check --write --unsafe / format-on-save for now: that's what rewrites ~9 unrelated files. I'm cleaning that debt up separately in #14 so it stops biting contributors — but you don't need to wait for it.)

So: that one import reorder + the README link-label fix from above, and you're good to merge. Sorry for the misdirection!

Rebased, fixed the import order + README label, and merged — thanks @CaptainLevi25! 🙌

hi @renezander030 .
Thanks a lot for fixing the mistakes that i have commited😂🫡.